Disambiguating Input Based On Context

ABSTRACT

In one implementation, a computer-implemented method includes receiving, at a mobile computing device, ambiguous user input that indicates more than one of a plurality of commands; and determining a current context associated with the mobile computing device that indicates where the mobile computing device is currently located. The method can further include disambiguating the ambiguous user input by selecting a command from the plurality of commands based on the current context associated with the mobile computing device; and causing output associated with performance of the selected command to be provided by the mobile computing device.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.12/851,881, filed on Aug. 6, 2010, which is herein incorporated byreference in its entirety.

TECHNICAL FIELD

This document generally describes methods, systems, and techniques fordisambiguating user input on a mobile computing device, such as a mobiletelephone.

BACKGROUND

Mobile computing devices (e.g., mobile telephones, smart telephones,personal digital assistants (PDAs), portable media players, etc.) havebeen configured to provide results to a user in response to unambiguousinput. For example, a user can submit a search query for directions to anearby pizzeria to a mobile computing device. In such an example, thesearch query unambiguously identifies that directions for a nearbypizzeria. In response, the mobile computing device can (alone, or incombination with a remote server system) identify a nearby pizzeria andprovide directions to the pizzeria to the user. Such mobile computingdevices have been configured to receive a search query as text-basedinput (e.g., a query typed using keys), selection-based input (e.g.,touchscreen selection, etc.), and audio-based input (e.g., voice input).When the query has some ambiguity, multiple results can be provided(with a highest scoring result at the top and ordered by decreasingrelevance) and a user can be given the opportunity to select one of theresults.

SUMMARY

In the techniques described in this document, the context of a computingdevice, such as a mobile telephone (e.g., smart phone, or app phone) istaken into consideration in order to disambiguate ambiguous user inputs.Ambiguous user input is input that, in the absence of relevantdisambiguating information, would be interpreted by the computing deviceor for the computing device (e.g., by a server system with which thecomputing device is in electronic communication) as corresponding tomore than one query or command. Ambiguous input may be particularlycommon for spoken input, in part because of the presence of homophones,and in part because a speech-to-text processor may have difficultydifferentiating words that are pronounced differently but sound similarto each other. For example, if a user says “search for sail/sale info”to a mobile computing device, this voice input can be ambiguous as itmay correspond to the command “search for sail info” (e.g., informationregarding a sail for a sailboat) or to the command “search for saleinfo” (information regarding a sale of goods). A device might evendetermine that the input was “search for sell info,” because “sell” and“sale” sound alike, particularly in certain dialects.

Using the techniques described here, ambiguous user input can bedisambiguated based on a context associated with a mobile computingdevice (and/or a user of the mobile computing device) that is separatefrom the user input itself, such as the physical location where themobile computing device is located (e.g., home, work, car, etc.), motionof the mobile computing device (e.g., accelerating, stationary, etc.),and recent activity on the mobile computing device (e.g., social networkactivity, emails sent/received, telephone calls made/received, etc.).For instance, if a user provides voice input “traffic” to a mobilecomputing device while travelling at a high rate of speed in a car, thevoice input may not be clearly received by the mobile computing devicebecause of ambient noise from the car (e.g., engine noise, wind, roadnoise, car stereo, etc.). Due to the lack of clarity for the voiceinput, the mobile computing device may interpret the voice input asbeing any of multiple different words that sound like “traffic,” such as“graphic.” To resolve the ambiguity with regard to the voice input(e.g., did the user say “traffic” or “graphic?”), the mobile computingdevice can determine that it is likely located in a car based, at leastin part, on the mobile computing device sensing that it is travelling ata high rate of speed (e.g., using any of a variety of motion sensorsthat are standard components of the device). Based on the mobilecomputing device's determined context (located in a car), the mobilecomputing device can determine that the user was more likely to havesaid “traffic” (as in automobile traffic on a road) than “graphic” andcan disambiguate the voice input to “traffic.”

In another example, a device that is docked may determine the type ofdock it is in, such as via physical electrical contacts on the dock anddevice that match each other, or via electronic communication (e.g., viaBluetooth or RFID) between the dock and the device. For example, acertain pin arrangement may be provided on a dock intended for home use,while a different arrangement may be provided for a dock intended andsold for in-car use. The device may then set its context as “in car” or“at home” based on such a determination. The device my then disambiguatespoken input such as “directions,” where the term could be interpretedas geographic directions (e.g., driving directions) in an “in car”context, and how-to directions (e.g., for cooking) in an “at home” mode.

In one implementation, a computer-implemented method includes receiving,at a mobile computing device, ambiguous user input that indicates morethan one of a plurality of commands; and determining a current contextassociated with the mobile computing device that indicates where themobile computing device is currently located. The method can furtherinclude disambiguating the ambiguous user input by selecting a commandfrom the plurality of commands based on the current context associatedwith the mobile computing device; and causing output associated withperformance of the selected command to be provided by the mobilecomputing device.

In another implementation, a system for disambiguating user inputincludes a mobile computing device and an input sub-system of the mobilecomputing device that is configured to receive ambiguous user input thatindicates more than one of a plurality of commands. The system canfurther include a context determination unit of the mobile computingdevice that is configured to determine a current context associated withthe mobile computing device that indicates where the mobile computingdevice is currently located. The system can also include an inputdisambiguation unit of the mobile computing device that is configured todisambiguate the ambiguous user input by selecting a command from theplurality of commands based on the current context associated with themobile computing device. The system can additionally include an outputsub-system of the mobile computing device that is configured to provideoutput associated with performance of the selected command.

In another implementation, a system for disambiguating user inputincludes a mobile computing device and an input sub-system of the mobilecomputing device that is configured to receive ambiguous user input thatindicates more than one of a plurality of commands. The system can alsoinclude a context determination unit of the mobile computing device thatis configured to determine a current context associated with the mobilecomputing device that indicates where the mobile computing device iscurrently located. The system can further include means fordisambiguating the ambiguous user input based on the current contextassociated with the mobile computing device, wherein the means fordisambiguating selects a command from the plurality of commands; and anoutput sub-system of the mobile computing device that is configured toprovide output associated with performance of the selected command.

The details of one or more embodiments are set forth in the accompanyingdrawings and the description below. Various advantages can be realizedwith certain implementations, such as permitting users to instruct amobile computing device to perform a desired task without requiring theuser to comply with all of the formalities of providing input for thedesired task. As features provided by a mobile computing device haveincreased, users may be required to provide their input with greaterspecificity so that the input is properly associated with the intendedfeature. However, such specificity can be cumbersome and difficult toremember. The described methods, systems, techniques, and mechanismsdescribed in this document can allow a user to provide input using lessspecificity than formally required for a feature yet still access theintended feature.

Other features, objects, and advantages of the invention will beapparent from the description and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIGS. 1A-B are conceptual diagrams of example mobile computing devicesfor disambiguating ambiguous user input.

FIGS. 2A-B are diagrams of an example system for disambiguatingambiguous user input on a mobile computing device.

FIG. 3 is a flowchart of an example technique for disambiguatingambiguous user input on a mobile computing device.

FIG. 4 is a conceptual diagram of a system that may be used to implementthe techniques, systems, mechanisms, and methods described in thisdocument.

FIG. 5 is a block diagram of computing devices that may be used toimplement the systems and methods described in this document, as eithera client or as a server or plurality of servers.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

This document describes techniques, methods, systems, and mechanisms fordisambiguating ambiguous user input on a mobile computing device (e.g.,mobile feature telephone, smart telephone (e.g., IPHONE, BLACKBERRY),personal digital assistant (PDA), portable media player (e.g., IPOD),etc.). As the features provided by mobile computing devices haveincreased, the number of commands recognized by a mobile computingdevice can increase as well. For example, each feature on a mobilecomputing device may register one or more corresponding commands that auser can type, speak, gesture, etc. to cause the feature to be launchedon the mobile computing device. However, as the number of recognizedcommands increases, commands can converge and make it more difficult todistinguish to which of multiple commands user input is intended tocorrespond. The problem is magnified for voice input. For example, voiceinput that is provided with loud background noise can be difficult toaccurately interpret and, as a result, can map to more than one commandrecognized by the mobile computing device. For instance, voice input“example” could be interpreted as, among other things, “egg sample,”“example,” or “exam pull.” As another example, the command “go to” mayrepresent “go to [geographic location]” for a mapping application, and“go to [artist/album/song]” for a media player.

Using the techniques described here, in response to receiving ambiguoususer input, a current context for the mobile device (and/or a user ofthe mobile computing device) can be determined and used to disambiguatethe ambiguous user input. A current context for a mobile computingdevice can include a variety of information associated with the mobilecomputing device and/or a user of the mobile computing device. Thecontext may be external to the device and represent a real time statusaround the device, such as a current physical location (e.g., home,work, car, located near wireless network “testnet2010,” etc.), adirection and rate of speed at which the device is travelling (e.g.,northbound at 20 miles per hour), a current geographic location (e.g.,on the corner of 10th Street and Marquette Avenue), and ambient noise(e.g., low-pitch hum, music, etc.). The context may also be internal tothe device, such as upcoming and/or recent calendar appointments (e.g.,meeting with John at 2:30 pm on Jul. 29, 2010), a time and date on aclock in the device (e.g., 2:00 pm on Jul. 29, 2010), recent deviceactivity (e.g., emails sent to John regarding the 2:30 meeting), andimages from the mobile computing devices camera(s).

The device can use the current context to select a command or query frommultiple commands or queries that would otherwise be suggested in theabsence of using the context. For example, if a user provides voiceinput “call Seth” to a mobile computing device using a wireless headset(e.g., BLUETOOTH headset) while driving on the freeway, ambient noisepicked up from traveling on the freeway may make the voice inputambiguous—the voice input can be interpreted as “call Beth” and “callSeth.” For the purposes of this example, assume that Beth and Seth areboth contacts in a list of telephone contacts for the user, but that theuser is travelling on the freeway toward Seth's house. The currentcontext for the mobile device can include, at least, that the mobilecomputing device is travelling on a freeway in an automobile headingtoward Seth's house (as determined by accessing a contact record forSeth that is associated with the user's device or an on-line account towhich the device is logged in). The context can be determined based on avariety of information associated with the mobile computing device, suchas the freeway background noise, the connection with the wirelessheadset, geographic positioning information (e.g., global positioningsystem (GPS) information), digital road maps, contact list information(e.g., Seth's address), etc. Based on the current context, the mobilecomputing device can disambiguated the ambiguous user voice input(interpreted as “call Seth” or “call Beth”) to “call Seth”—it appearsthat the user is travelling to meet up with Seth and may be calling toprovide an update on his/her status.

As described in further detail below, a mobile computing device candisambiguate ambiguous user input locally on the mobile computing deviceand/or in conjunction with a computer server system that is remote fromthe mobile computing device. For example, a mobile computing device candetermine its current context, disambiguate user input based on thecurrent context, and cause a command associated with the disambiguatedinput to be performed as a standalone device (e.g., without interactingwith other devices over a network). In another example, a mobilecomputing device can interact with a remote server system to determineits current context, disambiguate user input based on the currentcontext, and perform a command associated with the disambiguated input.The device can also determine its current context and send data thatidentifies the current content to a server system, which may thendisambiguate a user input.

In addition to using a device's context to disambiguate ambiguous input,a device may also provide output from performance of a command or query(or combination of command and a parameter that together make up aquery, such as “search for X”) associated with disambiguated input basedon the current context. For instance, if the mobile computing device isdetermined to have a current context of being located inside of a movingcar, the mobile computing device can switch into a “hands free” mode(e.g., activate microphone to receive voice input and provide audiooutput) for safety and can provide output accordingly.

The techniques, methods, systems, and mechanisms described in thisdocument for disambiguating user input can be used to disambiguate avariety of user input, not just input related to commands. For example,disambiguation based on a current context for a mobile computing deviceand/or a user of the mobile computing device can be used to select asuggested spelling for a misspelled word. For instance, if a user types“toad work” into a search field on a mobile computing device and thecurrent context for the mobile computing device includes the mobilecomputing device being located in an automobile, the mobile computingdevice can suggest the string “road work” to the user instead.

FIGS. 1A-B are conceptual diagrams 100 and 150 of example mobilecomputing devices 102 and 152 a-b for disambiguating ambiguous userinput 104 and 154. Referring to FIG. 1A, the example diagram 100provides an illustrative example of the mobile computing device 102receiving the ambiguous user input 104, determining a current contextfor the mobile computing device 102, disambiguating the ambiguous userinput 104 based on the determined current context, and providing outputthat is associated with performance of a command associated with thedisambiguated input.

In the example diagram 100, a user 103 is depicted as providing theambiguous user input 104 “Go To New York, New York” as voice input tothe mobile computing device 102. The mobile computing device 102 caninclude an input sub-system that includes a variety of devices, deviceinterfaces, and input interpretation modules that are configured toreceive audio input. For example, the user input 104 can be receivedusing a digital microphone that is part of the mobile computing device102 and/or a wireless interface connected to wireless headsets (e.g.,BLUETOOTH headsets), and interpreted using a speech recognition module.

The mobile computing device 102 can allow a user to employ commands 105that are associated with various features provided by the mobilecomputing device 102. For example, the command “Go To [GeographicLocation]” can correspond to a mapping and/or driving directions featurethat provides a map for and/or driving directions to a geographiclocation specified in the command. In another example, the command “GoTo [Song]” can correspond to a digital music player on the mobilecomputing device that is configured to play a song specified in thecommand. In a further example, the command “Go To [Web Page]” cancorrespond to a web browser application on the mobile computing devicethat is configured to request and provide a web page specified in thecommand.

As indicated by step A (106), upon receiving the user input 104 themobile computing device 102 can identify that the user input 104 isambiguous. User input can be identified as ambiguous for a variety ofreasons. Generally, user input is identified as being ambiguous if thesystem interprets it as having more than one likely intended meaning, inthe absence of attempts to disambiguate the input using the techniquesdescribed here. For instance, in the present example, the user input 104is identified as being ambiguous based on each of the commands 105possibly corresponding to the input 104—the user input 104 “Go To NewYork, New York” can indicate a geographic location (the city of NewYork, N.Y.), a song (the song “New York, New York”), and a web page (atourism web page for the city of New York, N.Y.). The commands 105 canbe identified as possibly corresponding to the input 104 using any of avariety of techniques, such as polling an application and/or servicecorresponding to each command (e.g., querying a music player associatedwith the command “Go To [Song]” to determine whether “New York, NewYork” is an accessible song on the mobile computing device 102),accessing one or more groups of permissible terms for each command(e.g., accessing a group of permissible geographic location terms forthe command “Go To [Geographic Location]”), etc.

User input, such as voice input, touch input (e.g., input receivedthrough a touchscreen), and key-based input (e.g., input receivedthrough a keypad/keyboard), can be identified as being ambiguous for avariety of reasons. For instance, as indicated in the example diagram100, user input can be ambiguous when it corresponds to multipledifferent commands, regardless of whether the user input is voice input.For example, if the user input 104 is text-based input instead of voiceinput, as depicted, the mobile computing device 102 can still identifythe user input 104 as ambiguous.

In another example, voice input that is identified as being a homophone(multiple terms with the same pronunciation but different meanings)and/or a homonym (multiple terms with the same spelling andpronunciation but different meaning) can be identified as ambiguous. Forexample, voice input that is interpreted as “fair,” “sale,” “waist,”“example,” “wore,” and “cereal” are homophones (same pronunciation) of“fare,” “sail,” “waste,” “egg sample,” “war,” and “serial,”respectively, and can be identified as ambiguous. In another example,voice input that is interpreted as “tire” and “bank” are homonyms(“tire” can be part of a wheel (e.g., car tire) or a state ofexhaustion; “bank” can be a place where money is stored or river bank)and can be identified as ambiguous.

Additionally, terms that are heteronyms (different pronunciations butwith the same spelling) may be identified as ambiguous. Although theintended meaning of a heteronym may be conveyed by voice input throughdifferent pronunciations, this intended meaning may be removed when thevoice input is converted text through speech recognition. For example,the term “close” can be pronounced differently when it is used toindicate proximity (e.g., “the store is close to your current location”)and when it is used as a command (e.g., “please close the door”).However, when converted through speech recognition to text for use bythe mobile computing device 102, the different pronunciations can becollapsed to the same term “close” and can be identified as ambiguous.

Furthermore, poor audio quality associated with voice input can causeotherwise unambiguous user input to be identified by the mobilecomputing device 102 as ambiguous. For instance, if the user 103provides the user input 104 to the mobile computing device 102 from alocation with a significant amount of background noise, the user input104 may be received by the mobile computing device 102 with poor audioquality (e.g., the primary audio signal is washed out by backgroundaudio signals). User input received with poor audio quality can beidentified by the mobile computing device 102 as ambiguous.

In another example, touch and key-based input can also be identified bythe mobile computing device 102 as ambiguous. For instance, misspelledwords typed by a user using a touchscreen or a keypad/keyboard can beidentified as ambiguous. In another example, homographs (multiple wordswith the same spelling but different meaning) can be identified asambiguous, similar to the examples provided above with regard tohomophones.

With the ambiguous user input 106 identified (106), at step B a currentcontext for the mobile device 102 can be determined (108). The currentcontext includes information that describes the present state and/orsurroundings of the mobile computing device 102 and/or the user of themobile computing device at the time the input 106 is received. Forinstance, the current context can include a variety of informationrelated to the mobile computing device 102 and the user, such asinformation regarding the surrounding physical environment (e.g.,available networks, connections to other nearby computing devices,geographic location, weather conditions, nearby businesses, volume ofambient noise, level of ambient light, image captured by the mobiledevice's camera, etc.), the present state of the mobile computing device102 (e.g., rate of speed, touchscreen input activated, audio inputactivated, ringer on/off, etc.), time and date information (e.g., timeof day, date, calendar appointments, day of the week, etc.), useractivity (e.g., recent user activity, habitual user activity), etc. Thecurrent context can be determined by the mobile computing device 102using data and sensors that are local and/or remote to the mobilecomputing device 102.

As indicated by the example context 110 for the mobile device, thecurrent context for the mobile computing device includes ambient noiselevel information 112 a, geographic location information 112 b,available network information 112 c, rate of speed information 112 d,and device activity information 112 e. In the depicted example, theambient noise level information 112 a indicates that there is a highlevel of ambient noise and the geographic information 112 b providesthat the mobile computing device 102 is currently located on a road. Theavailable network information 112 c provides that an automobileBLUETOOTH network is available to the mobile computing device 102 (e.g.,BLUETOOTH connection with an automobile stereo system) and the rate ofspeed information 112 d indicates that the mobile computing device 102is currently travelling at 50 miles per hour. The device activityinformation 112 e indicates that telephone calls to one or moretelephone numbers associated with New York, N.Y., have recently beenmade using the mobile computing device 102.

At step C, the mobile computing device 102 can disambiguate the userinput 104 based on the current context 110 (114). For instance, based onthe geographic location information 112 b and the rate of speedinformation 112 d, it can be inferred that the mobile computing device102 is travelling in a vehicle of some sort (e.g., a car, a bus, etc.).This inference can further be supported by the high level of ambientnoise generated during high speed road travel, as indicated by theambient noise level information 112 a. The mobile computing device 102can further be identified as travelling in a car (instead of on a bus)based on the available automobile BLUETOOTH network, as indicated by theavailable network information 112 c.

Based on the context of the mobile computing device 102 (travelling in acar on a highway of some sort), it is more likely that the user input104 corresponds to the “Go To [Geographic Location]” command or to the“Go To [Song]” command than to the “Go To [Web Page]” command—a user ina car may be more likely to want a map/driving directions or to listento music than to view a web page. Both the “Go To [Geographic Location]”command and the “Go To [Song]” command seem likely given the currentcontext.

However, given that the mobile computing device 102 has recently beenused to place telephone calls to a telephone number associated with alocation in New York, N.Y., it can be inferred that the user 103 and themobile computing device 102 are likely travelling to a destination inNew York, N.Y. For instance, the user 103 may have recently called toconfirm his/her reservation at a hotel in New York where he/she will bestaying. Based on the inference that the user 103 and the mobilecomputing device 102 are travelling to New York, the “Go To [GeographicLocation]” command can be selected from among the commands 105 as beingthe command most likely intended by the user 103 with the user input104.

At step D, output for the disambiguated command (“Go To [GeographicLocation]”) can be provided on the mobile computing device 102 (116).For example, a map 118 depicting driving directions from the currentgeographic location of the mobile computing device 102 to New York,N.Y., can be provided on the mobile computing device 102.

As indicated above, the manner in which output is provided on the mobilecomputing device 102 can be selected based on the current context 110.For instance, in the present example, the mobile computing device 102 isdetermined to be travelling in a car at a high rate of speed on ahighway. It may be dangerous to only present the directions visually asthe map 118 on the mobile computing device 102, as it will likely take auser's focus off the road. However, the driving directions could beprovided audibly by the mobile computing device 102 in addition to (orinstead of) the map 118.

As discussed previously, some portions of the steps A-D (106, 108, 114,and 116) can be performed locally on the mobile computing device 102and/or in conjunction with a remote system. For example, the mobilecomputing device 102 can provide the received voice-based user input 104from the user 103 to a remote system that implements a robust speechrecognition service over a network. In response, the mobile computingdevice 102 can receive transcribed text for the user input 104 from theremote system. The distribution of the steps A-D (106, 108, 114, and116) across the mobile computing device 102 and one or more remotesystems can vary. For example, in some implementations, the mobilecomputing device 102 can perform all of the steps A-D locally as astandalone device. In some implementations, at least a portion of thesteps A-D can be performed in conjunction with a remote system.

Referring to FIG. 1B, the example diagram 150 provides an illustrativeexample of how disambiguation of user input 154 can be differentdepending on a context associated with a mobile computing device 152a-b. In this example, the mobile computing device 152 a-b is intended todemonstrate alternate paths that can result in different contexts inresponse to the user input 154.

Similar to the ambiguous user input 104 discussed above with regard toFIG. 1A, the user input 154 can be identified as ambiguous. In the firstalternate path 156 a, the mobile computing device 152 a is located in auser's home 158. The context for the mobile computing device 152 a isdepicted as including a desktop computer 160, a television 162, a laptopcomputer 164, a wireless router 166, a media computing device 168,available networks 170, and a mobile device dock 172. Each of devices160-172 may output a signal (e.g., sound, wireless data/networktransmission, etc.) that the mobile computing device 152 a can detectdirectly or indirectly. For example, the television 162 can outputsound, light, and/or a wireless networking signal that the mobilecomputing device 152 a can detect. In another example, the mobilecomputing device 152 a can identify a wireless router 166 that providesa wireless network for the user's home 158 as well as other availablenetworks 170, such as the wireless networks of the user's neighbors,cellular telephone networks, etc.

Similarly, the mobile computing device 152 a can detect each of thedevices 160-172 through direct and/or indirect connections with thedevices 160-172. For example, the mobile computing device 152 a canconnect to a home network through the wireless router 166, though whichthe mobile computing device 152 a can communicate with the devices160-172. In another example, the mobile computing device 152 a canidentify the mobile device dock 172 through a physical dockingconnection. For instance, the mobile device dock 172 may be a stereosystem with which the mobile computing device 152 a can be docked toplay music.

The mobile computing device 152 a can determine that it is physicallylocated at the user's home 158 based on the detected proximity of one ormore of the devices 160-172. For example, the mobile computing device152 a can determine when a wireless network “examplenet1234” provided bythe wireless router 166 is available, that the mobile computing device152 a is located in or near the home 158.

As described above with regard to FIG. 1A, the mobile computing device152 a can disambiguate the user input 154 based on the current contextfor the mobile computing device 152 a. In this example, the currentcontext includes the mobile computing device 152 a being located at thehome 158 and physically connected to the mobile device dock 172, throughwhich the mobile computing device 152 a can play music. Based on thecurrent context, the ambiguous user input 154 can be disambiguated toone of the commands 105 discussed above with regard to FIG. 1A. In thepresent example, the ambiguous user input 154 is disambiguated to the“Go To [Song]” command based on the mobile computing device 152 a beingstationary (not travelling) and being able to play music through aconnection with the mobile device dock 172. As illustrated by thedisplay 174 on the mobile computing device 152 a, the disambiguated userinput (selection of the command “Go To [Song]” from the ambiguous userinput 154) can be used to play the song “New York, New York” by FrankSinatra.

In contrast, the different context for the mobile computing device 152b, which is located in a car 176, can cause the mobile computing device152 b to disambiguate the user input 154 differently than the mobilecomputing device 152 a. The mobile computing device 152 b can determinethat it is located in the car 176 based on ambient car noises 178 (e.g.,engine noise, wind, etc.), a signal from and/or connection to a wirelessheadset 180, a connection with the docking/charging cable 182 (e.g., amobile computing device charger powered off a cigarette lighter outletin the car 176), and a connection with an automobile stereo system 184(e.g., a wireless BLUETOOTH connection through which the mobilecomputing device can stream audio data to be played on the stereo system184). The presence of one or more of the detected features 178-184 canindicate that the mobile computing device 152 b is physically located inthe car 176.

Similar to the disambiguation of the user input 104 described above withregard to mobile computing device 102, the mobile computing device 152 bcan disambiguate the user input 154 by selecting the “Go To [GeographicLocation]” command from the commands 105 based on the device's currentcontext, which includes being located in the car 176. Output fromperformance of the selected command is illustrated by a map 186displayed on the mobile computing device 152 b that provides drivingdirections to New York, N.Y.

FIGS. 2A-B are diagrams of an example system 200 for disambiguatingambiguous user input on an example mobile computing device 202. Themobile computing device 202 can be configured to disambiguate ambiguoususer input based upon a current context associated with the mobilecomputing device 202 and/or a user of the mobile computing device,similar to the mobile computing devices 102 and 152 a-b described abovewith regard to FIGS. 1A-B.

The mobile computing device 202 is depicted as including an inputsubsystem 204 through which a user of the mobile computing device 202can provide ambiguous user input. Referring to FIG. 2B, the inputsubsystem 204 is depicted as including a microphone 206 a (configured toreceive audio-based input), a keyboard 206 b (configured to receivekey-based input), a touchscreen 206 c (configured to receive screentouch-based input), an accelerometer 206 d (configured to receivemotion-based input), a trackball 206 e (configured to receive GUIpointer-based input), a camera 206 f (configured to receive visualinput), and a light sensor 206 g (configured to receive input based onlight intensity). The input subsystem 204 also includes a networkinterface 208 (e.g., wireless network interface, universal serial bus(USB) interface, BLUETOOTH interface, public switched telephone network(PSTN) interface, Ethernet interface, cellular network interface, 3Gand/or 4G network interface, etc.) that is configured to receivenetwork-based input and output. Other types of input devices notmentioned may also be part of the input subsystem 204.

An input parser 210 of the mobile computing device 202 can be configuredto receive input from the input subsystem 204 (e.g., input events) anddetermine whether the received input is ambiguous. The input parser 210can include a variety of modules to interpret user input, such as aspeech recognition module 211 a, a computer vision module 211 b, and agesture interpretation module 211 c. The speech recognition module 211 acan interpret audio-based input received through the input subsystem204, such as converting voice input received by the microphone 206 ainto text. The computer vision module 211 b can interpret image-basedinput received through the input subsystem 204, such as identifyingobjects in video received through the camera 206 f. The gestureinterpretation module 211 c can interpret gesture-based input receivedthrough the input subsystem 204, such as determining whether gestureinformation received through the accelerometer 206 d and one or moregyroscopes (not depicted) corresponds to a predefined gesture on themobile computing device 202.

The input parser 210 can use input rules 212 to determine whether aparticular input is ambiguous and in need of disambiguation. Forinstance, the input rules 212 can identify a threshold level of audioquality below which received audio input is determined to be ambiguous.In another example, the input rules 212 can provide terms and phrasesthat are ambiguous when received as voice input, such as homophones. Theuser input rules 212 can also include the other examples of identifyinguser input as ambiguous described above with regard to FIG. 1A. Theinput rules 212 can be preconfigured and/or user defined.

In response to the input parser 210 identifying input that is ambiguous,a mobile device context determination unit 214 can determine a currentcontext for the mobile computing device 202. The mobile device contextdetermination unit 214 can determine a current context for the mobiledevice 202 using a variety of context monitoring units of the mobilecomputing device 202.

For instance, a global positioning system (GPS) unit 216 can providegeographic location information to the mobile device contextdetermination unit 214 and a travel monitor unit 218 (in conjunctionwith a travel data repository 220) can provide information related to aroute currently being traveled and habitual routes traveled by themobile computing device 202. An activity monitor unit 222 (inconjunction with an activity data repository 224) can provideinformation related to recent and habitual user activity (e.g.,applications used, specific information accessed at various times, etc.)on the mobile device 202. A location monitor unit 226 can provideinformation regarding a current physical location (e.g., home, work, ina car, etc.) for the mobile computing device 202. The location monitorunit 226 can use a location data repository 227 to determine the currentphysical location. The location data repository 227 can associateinformation regarding the mobile computing device 202's detectedsurroundings (e.g., available wireless networks, ambient sounds, nearbycomputing devices, etc.) with physical locations. The location monitorunit 226 can also identify entities (e.g., businesses, parks, festivals,public transportation, etc.) that are physically located near the mobiledevice 202.

A time and date unit 228 can provide current time and date informationand a calendar unit 230 (in conjunction with a calendar data repository232) can provide information related to appointments for the user. Anemail unit 234 (in conjunction with an email data repository 236) canprovide email-related information (e.g., recent emails sent/received).The mobile context determination unit 214 can receive information fromother context monitoring units not mentioned or depicted.

In some implementations, the context monitoring units 216-236 can beimplemented in-part, or in-whole, remote from the mobile computingdevice 202. For example, the email unit 234 may be a thin-client thatmerely displays email-related data that is maintained and provided by aremote server system. In such an example, the email unit 234 caninteract with the remote server system to obtain email-relatedinformation to provide to the mobile device context determination unit214.

A disambiguation unit 238 can use the current context for the mobiledevice 202, as determined by the mobile device context determinationunit 214, to disambiguate user input that has been determined to beambiguous by the input parser 210. The current context of the mobilecomputing device 202 can be used to infer which of multipledisambiguation candidates was intended by the user. Referring to theexample described above with regard to FIG. 1A, each of the commands 105can be considered a disambiguation candidate—a possible command that canbe selected for the received ambiguous user input 104. From the currentcontext 110 of the mobile computing device 102, the user input 104 wasinferred as indicating a request for a map/driving directions instead ofa request to play music or access a web page.

The disambiguation unit 238 can use information stored in adisambiguation inference data repository 240 that associates variouscontext scenarios with various inferences that can be used todisambiguate user input. For example, the disambiguation inference datarepository 240 can include information that indicates that when thecurrent context of the mobile computing device 202 includes beingphysically located in a car, the user is more likely to be interested indriving directions than in viewing a web page. The information stored inthe disambiguation inference data repository 240 can be user definedand/or predefined.

The disambiguation inference data repository 240 can be used inconjunction with a user behavior data repository 242 by thedisambiguation unit 238 to disambiguate user input. The user behaviordata repository 242 can log previous ambiguous user input, a context forthe mobile device 202 at the time of the ambiguous user input, previousdisambiguation of the user input by the disambiguation unit 238, and theuser's subsequent behavior (e.g., user appeared to use the information,user immediately provided clarifying input, etc.) with respect to outputprovided based on the disambiguated user input. The user behavior datastored in the user behavior data repository 242 can indicate whetherdisambiguation of a user's ambiguous input based on the context of thedevice 202 was what the user intended with the ambiguous user input.

For example, if the user is provided with driving directions in responseto ambiguous user input and the mobile device 202 is determined totravel to a destination according to the driving directions, then theassociated user behavior data can indicate that the user found thedisambiguation of the user input based on the device's context to bewhat the user intended with the input. In another example, if the useris provided with driving directions in response to ambiguous user inputand the user immediately provides additional input indicating that theuser would like for music to be played, then the associated userbehavior can indicate that the user found the disambiguation of the userinput to not be what the user intended.

The disambiguation unit 238 can use user behavior data from the userbehavior data repository 242 to infer what the user intended with theambiguous user input. For example, the disambiguation unit 238 canattempt to identify previous contexts that are similar to a currentcontext for the mobile device 202 to receive an indication regardingwhat the user intended with ambiguous user input.

Using disambiguated user input provided by the disambiguation unit 238,an input processing unit 244 can process the disambiguated user input.In some implementations, the input processing unit 244 can forward thedisambiguated user input to an application and/or service that isassociated with the user input (e.g., provide a disambiguated request toplay music to a music player application). In some implementations, theinput processing unit 244 can cause one or more operations associatedwith the disambiguated user input to be performed. For instance, theinput processing unit 244 may communicate with a remote server systemthat is configured to perform at least a portion of the operationsassociated with the disambiguated input.

As described above with regard to FIGS. 1A-B, commands associated withdisambiguated user input can be performed local and/or remote to themobile computing device 202. For instance, in implementations where acalendar application is implemented locally on the mobile computingdevice 202, disambiguated user input that indicates a request forcalendar information can be performed locally on the mobile computingdevice 202 (e.g., querying the calendar unit 230 for relevant calendarinformation stored in the calendar data repository 232). Additionally,the mobile computing device 202 can determine its current context anddisambiguate ambiguous user input as a standalone device (e.g., withoutinteracting with a remote server system over a network). In anotherexample, in implementations where a calendar data for a calendarapplication is provided on a remote server system, the mobile computingdevice 202 can interact with the remote server system to access therelevant calendar information.

An output subsystem 246 of the mobile computing device 202 can provideoutput obtained by the input processing unit 244 to a user of the device202. The output subsystem 246 can include a variety of output devices,such as a display 248 a (e.g., a liquid crystal display (LCD), atouchscreen), a projector 248 a (e.g., an image projector capable ofprojecting an image external to the device 202), a speaker 248 c, aheadphone jack 248 d, etc. The network interface 208 can also be part ofthe output subsystem 246 and may be configured to provide the resultsobtained by the result identification unit 244 (e.g., transmit resultsto BLUETOOTH headset).

Referring to FIG. 2A, the mobile computing device 202 can wirelesslycommunicate with wireless transmitter 250 (e.g., a cellular networktransceiver, a wireless network router, etc.) and obtain access to anetwork 252 (e.g., the Internet, PSTN, a cellular network, a local areanetwork (LAN), a virtual private network (VPN), etc.). Through thenetwork 252, the mobile computing device 202 can be in communicationwith a mobile device server system 254 (one or more networked servercomputers), which can be configured to provide mobile device relatedservices and data to the mobile device 202 (e.g., provide calendar data,email data, connect telephone calls to other telephones, etc.).

The mobile device 202 can also be in communication with one or moreinformation server systems 256 over the network 252. Information serversystems 256 can be server systems that provide information that may berelevant to processing user input. For instance, the information serversystems 256 can provide current traffic conditions, up-to-date drivingdirections, a weather forecast, and information regarding businesseslocated near the current geographic location for the mobile device 202.

FIG. 3 is a flowchart of an example technique 300 for disambiguatingambiguous user input on a mobile computing device. The example technique300 can be performed by any of a variety of mobile computing devices,such as the mobile computing devices 102 and 152 a-b described abovewith regard to FIGS. 1A-B and/or the mobile computing device 202described above with regard to FIGS. 2A-B.

The technique 300 starts at step 302 by receiving user input. The userinput can be any of a variety of input, such as key-based input(keyboard/keypad input), touch-based input on a touchscreen, voiceinput, gesture input (performing a physical gesture with the mobilecomputing device), etc. For example, the mobile computing device 102receives the voice input 104, as described with regard to FIG. 1A. Inanother example, the mobile computing device 202 can receive user inputusing the input subsystem 204, as described with regard to FIGS. 2A-B.

In some implementations, speech recognition with regard to the userinput can be performed (step 304). For instance, the speech recognitionmodule 211 a can convert voice input received through the inputsubsystem 204 of the mobile computing device 202 into text. The speechrecognition module 211 a can also be used in situations where theambiguous user input is not voice input. For example, if the user inputis touch or key-based input, the speech recognition module 211 a may beused to audibly identify background speech when the input is receivedfor the purpose of determining a context associated with the mobilecomputing device 202.

The user input is identified as ambiguous (step 306). For example, themobile computing device 202 can use the input parser 210 and the inputrules 212 to identify user input that is ambiguous, as described abovewith regard to FIGS. 2A-B. For instance, user input can be identified asbeing ambiguous if it can be interpreted as having more than onepossible intended meaning. For instance, the command “Go To New York,New York” can be interpreted as possibly corresponding to the command“Go To [Geographic Location]” and to the command “Go To [Song],” asdescribed above with regard to FIG. 1A.

A variety of steps can be performed to obtain information that indicatesa current context for a mobile device. For example, in someimplementations one or more ambient sounds can be detected (step 308),one or more physical object located nearby the mobile computing devicecan be optically identified (step 310), and/or one or more othercomputing devices located nearby the mobile computing device can beidentified (step 312). For example, the input parser 210 can useinformation obtained by the input subsystem 204 in conjunction with theuser input to make such determinations. For instance, the speechrecognition module 211 a can be used to detect ambient sounds and todetermine whether the ambient sounds correspond to speech and/or toother objects (e.g., car, television, dish washer, pet, wind, etc.). Inanother example, the computer vision module 211 b can be used tooptically identify physical objects based on images obtained from thecamera 206 f of the mobile computing device 202. In a further example,the network interface 208 can be used to identify other computingdevices based available wired and/or wireless connections to the othercomputing devices. Other steps for obtaining information to determine acurrent context for a mobile computing device that are not explicitlydescribed may also be part of the technique 300.

In some implementations, information that associates the other computingdevices with physical locations can be accessed (step 314). Physicallocations can correspond to physical structures, which may not be tiedto a particular geographic location. For instance, a physical structurecan be mobile, such as a car or a train. Such mobile physical structurescan move from one geographic location to another (e.g., a car travelfrom Los Angeles, Calif., to San Francisco, Calif.). However, somephysical structures are stationary and tied to a particular geographiclocation, such as a skyscraper. Referring to FIG. 2B as an example, thelocation data 227 can provide information that associates the othercomputing devices with physical locations, such as a car or a house.

Using the information detected, identified, and accessed in steps308-314, as well as other context-related information not explicitlydescribed with regard to this technique, the current context for themobile computing device can be determined (step 316). For example, themobile device context determination unit 214 of the mobile computingdevice 202 can be used to determine a current context for the mobilecomputing device 202, as described above with regard to FIGS. 2A-B. Forinstance, the current context of the mobile computing device 102 isdetermined to indicate that the mobile computing device 102 istravelling in a car with a likely destination of New York, N.Y., asdescribed above with regard to FIG. 1A.

The user input can be disambiguated based on the current context for themobile computing device (step 318). For example, the disambiguation unit238 of the mobile computing device 202 can use the current context, asdetermined by the context determination unit 214, to disambiguate theambiguous user input received through the input subsystem 204. Asdescribed above with regard to FIG. 1A, the user input “Go To New York,New York” can be disambiguated to the command “Go To [GeographicLocation]” based on the determined context 110 for the mobile computingdevice 102.

In some implementations, a determination can be made as to whether acommand selected for the ambiguous user input applies to one or more ofthe identified other computing devices (step 320). For example, theinput processing unit 244 can determine whether the selected commandshould be performed by and/or output associated with performance of theselected command should be provided on one of the other identifiedcomputing devices. For instance, if the mobile computing device 202identifies that a television is accessible to the mobile computingdevice 202 (e.g., the mobile computing device can electronicallycommunicate with the television and instruct the television to displaycontent) and the selected command pertains to playing a video, the inputprocessing unit 214 can determine that the selected command pertains tothe identified television.

Based on the determination made in step 320, the mobile computing devicecan communicate with the identified other computing device (step 322).Expanding upon the example from the previous paragraph, the mobilecomputing device 202 can communicate with the identified television tocause the selected command (play a video) to be performed and/or outputby the television (e.g., play the video on the television).

In some implementations, a mode of operation for the mobile computingdevice can be selected (step 324). A mode of operation can pertain tothe manner in which output is provided by the mobile computing deviceand can be used to determine which components of the output subsystem246 are used to provide output to a user. A few example modes ofoperations include: a voice-only mode of operation during which themicrophone 206 a of the mobile computing device 202 is activated toreceived voice input and the speaker 248 c of the mobile computingdevice 202 is used to provide output; a silent mode of operation duringwhich the speaker 248 c of the mobile computing device 202 isdeactivated and a display 248 a of the mobile computing device 202 isused to provide output; and a user-defined mode of operation duringwhich the microphone 206 a, the speaker 248 c, and the display 248 a ofthe mobile computing device 202 are used to receive input and to provideoutput according to user-defined settings for the mobile computingdevice 202. The mode of operation can be selected by the mobilecomputing device 202 based on a variety of factors, including thedetermined current context for the mobile computing device 202.

Output associated with the selected command can be caused to be providedin association with the mobile computing device (step 326). For example,the output subsystem 246 of the mobile computing device 202 can provideoutput based on performance of the selected command. The output can beprovided on the mobile computing device 202 in accordance with theselected mode of operation. In another example, one of the identifiedother computing devices, such as the television described above, can beselected and caused to provide output for the selected command.

In some implementations, second user input can be received (step 328)and a determination can be made as to whether the ambiguous user inputwas correctly disambiguated based on the received second input (step330). For example, if, after providing output associated withperformance of the disambiguated user input, the user provides secondinput that clarifies the previously received ambiguous input (e.g.,provide voice command “Go To Song New York, New York” after drivingdirections are displayed for the command “Go To New York, New York”),the mobile computing device 202 may determine that the ambiguous userinput was not disambiguated correctly. However, if the second inputfurther interacts with the output provided based on the disambiguation(e.g., zoom in on a portion of the driving directions provided for thecommand “Go To New York, New York”), the mobile computing device 202 maydetermine that the ambiguous user input was correctly disambiguated.Based on the determination of whether the ambiguous user input wascorrectly disambiguated, user behavior data can be updated (step 332).For instance, the user behavior data 242 can be updated to reflectwhether the ambiguous user input was correctly disambiguated for thecurrent context and stored for subsequent use by the disambiguation unit238 when attempting to disambiguate user input.

FIG. 4 is a conceptual diagram of a system that may be used to implementthe techniques, systems, mechanisms, and methods described in thisdocument. Mobile computing device 410 can wirelessly communicate withbase station 440, which can provide the mobile computing device wirelessaccess to numerous services 460 through a network 450.

In this illustration, the mobile computing device 410 is depicted as ahandheld mobile telephone (e.g., a smartphone or an applicationtelephone) that includes a touchscreen display device 412 for presentingcontent to a user of the mobile computing device 410. The mobilecomputing device 410 includes various input devices (e.g., keyboard 414and touchscreen display device 412) for receiving user-input thatinfluences the operation of the mobile computing device 410. In furtherimplementations, the mobile computing device 410 may be a laptopcomputer, a tablet computer, a personal digital assistant, an embeddedsystem (e.g., a car navigation system), a desktop computer, or acomputerized workstation.

The mobile computing device 410 may include various visual, auditory,and tactile user-output mechanisms. An example visual output mechanismis display device 412, which can visually display video, graphics,images, and text that combine to provide a visible user interface. Forexample, the display device 412 may be a 3.7 inch AMOLED screen. Othervisual output mechanisms may include LED status lights (e.g., a lightthat blinks when a voicemail has been received).

An example tactile output mechanism is a small electric motor that isconnected to an unbalanced weight to provide a vibrating alert (e.g., tovibrate in order to alert a user of an incoming telephone call orconfirm user contact with the touchscreen 412). Further, the mobilecomputing device 410 may include one or more speakers 420 that convertan electrical signal into sound, for example, music, an audible alert,or voice of an individual in a telephone call.

An example mechanism for receiving user-input includes keyboard 414,which may be a full qwerty keyboard or a traditional keypad thatincludes keys for the digits ‘0-4’, ‘*’, and ‘#’. The keyboard 414receives input when a user physically contacts or depresses a keyboardkey. User manipulation of a trackball 416 or interaction with a trackpadenables the user to supply directional and rate of rotation informationto the mobile computing device 410 (e.g., to manipulate a position of acursor on the display device 412).

The mobile computing device 410 may be able to determine a position ofphysical contact with the touchscreen display device 412 (e.g., aposition of contact by a finger or a stylus). Using the touchscreen 412,various “virtual” input mechanisms may be produced, where a userinteracts with a graphical user interface element depicted on thetouchscreen 412 by contacting the graphical user interface element. Anexample of a “virtual” input mechanism is a “software keyboard,” where akeyboard is displayed on the touchscreen and a user selects keys bypressing a region of the touchscreen 412 that corresponds to each key.

The mobile computing device 410 may include mechanical or touchsensitive buttons 418 a-d. Additionally, the mobile computing device mayinclude buttons for adjusting volume output by the one or more speakers420, and a button for turning the mobile computing device on or off. Amicrophone 422 allows the mobile computing device 410 to convert audiblesounds into an electrical signal that may be digitally encoded andstored in computer-readable memory, or transmitted to another computingdevice. The mobile computing device 410 may also include a digitalcompass, an accelerometer, proximity sensors, and ambient light sensors.

An operating system may provide an interface between the mobilecomputing device's hardware (e.g., the input/output mechanisms and aprocessor executing instructions retrieved from computer-readablemedium) and software. Example operating systems include the ANDROIDmobile computing device platform; APPLE IPHONE/MAC OS X operatingsystems; MICROSOFT WINDOWS 7/WINDOWS MOBILE operating systems; SYMBIANoperating system; RIM BLACKBERRY operating system; PALM WEB operatingsystem; a variety of UNIX-flavored operating systems; or a proprietaryoperating system for computerized devices. The operating system mayprovide a platform for the execution of application programs thatfacilitate interaction between the computing device and a user.

The mobile computing device 410 may present a graphical user interfacewith the touchscreen 412. A graphical user interface is a collection ofone or more graphical interface elements and may be static (e.g., thedisplay appears to remain the same over a period of time), or may bedynamic (e.g., the graphical user interface includes graphical interfaceelements that animate without user input).

A graphical interface element may be text, lines, shapes, images, orcombinations thereof. For example, a graphical interface element may bean icon that is displayed on the desktop and the icon's associated text.In some examples, a graphical interface element is selectable withuser-input. For example, a user may select a graphical interface elementby pressing a region of the touchscreen that corresponds to a display ofthe graphical interface element. In some examples, the user maymanipulate a trackball to highlight a single graphical interface elementas having focus. User-selection of a graphical interface element mayinvoke a pre-defined action by the mobile computing device. In someexamples, selectable graphical interface elements further oralternatively correspond to a button on the keyboard 404. User-selectionof the button may invoke the pre-defined action.

In some examples, the operating system provides a “desktop” userinterface that is displayed upon turning on the mobile computing device410, activating the mobile computing device 410 from a sleep state, upon“unlocking” the mobile computing device 410, or upon receivinguser-selection of the “home” button 418 c. The desktop graphicalinterface may display several icons that, when selected with user-input,invoke corresponding application programs. An invoked applicationprogram may present a graphical interface that replaces the desktopgraphical interface until the application program terminates or ishidden from view.

User-input may manipulate a sequence of mobile computing device 410operations. For example, a single-action user input (e.g., a single tapof the touchscreen, swipe across the touchscreen, contact with a button,or combination of these at a same time) may invoke an operation thatchanges a display of the user interface. Without the user-input, theuser interface may not have changed at a particular time. For example, amulti-touch user input with the touchscreen 412 may invoke a mappingapplication to “zoom-in” on a location, even though the mappingapplication may have by default zoomed-in after several seconds.

The desktop graphical interface can also display “widgets.” A widget isone or more graphical interface elements that are associated with anapplication program that has been executed, and that display on thedesktop content controlled by the executing application program. Unlikean application program, which may not be invoked until a user selects acorresponding icon, a widget's application program may start with themobile telephone. Further, a widget may not take focus of the fulldisplay. Instead, a widget may only “own” a small portion of thedesktop, displaying content and receiving touchscreen user-input withinthe portion of the desktop.

The mobile computing device 410 may include one or morelocation-identification mechanisms. A location-identification mechanismmay include a collection of hardware and software that provides theoperating system and application programs an estimate of the mobiletelephone's geographical position. A location-identification mechanismmay employ satellite-based positioning techniques, base stationtransmitting antenna identification, multiple base stationtriangulation, internet access point IP location determinations,inferential identification of a user's position based on search enginequeries, and user-supplied identification of location (e.g., by“checking in” to a location).

The mobile computing device 410 may include other application modulesand hardware. A call handling unit may receive an indication of anincoming telephone call and provide a user capabilities to answer theincoming telephone call. A media player may allow a user to listen tomusic or play movies that are stored in local memory of the mobilecomputing device 410. The mobile telephone 410 may include a digitalcamera sensor, and corresponding image and video capture and editingsoftware. An internet browser may enable the user to view content from aweb page by typing in an addresses corresponding to the web page orselecting a link to the web page.

The mobile computing device 410 may include an antenna to wirelesslycommunicate information with the base station 440. The base station 440may be one of many base stations in a collection of base stations (e.g.,a mobile telephone cellular network) that enables the mobile computingdevice 410 to maintain communication with a network 450 as the mobilecomputing device is geographically moved. The computing device 410 mayalternatively or additionally communicate with the network 450 through aWi-Fi router or a wired connection (e.g., Ethernet, USB, or FIREWIRE).The computing device 410 may also wirelessly communicate with othercomputing devices using BLUETOOTH protocols, or may employ an ad-hocwireless network.

A service provider that operates the network of base stations mayconnect the mobile computing device 410 to the network 450 to enablecommunication between the mobile computing device 410 and othercomputerized devices that provide services 460. Although the services460 may be provided over different networks (e.g., the serviceprovider's internal network, the Public Switched Telephone Network, andthe Internet), network 450 is illustrated as a single network. Theservice provider may operate a server system 452 that routes informationpackets and voice data between the mobile computing device 410 andcomputing devices associated with the services 460.

The network 450 may connect the mobile computing device 410 to thePublic Switched Telephone Network (PSTN) 462 in order to establish voiceor fax communication between the mobile computing device 410 and anothercomputing device. For example, the service provider server system 452may receive an indication from the PSTN 462 of an incoming call for themobile computing device 410. Conversely, the mobile computing device 410may send a communication to the service provider server system 452initiating a telephone call with a telephone number that is associatedwith a device accessible through the PSTN 462.

The network 450 may connect the mobile computing device 410 with a Voiceover Internet Protocol (VoIP) service 464 that routes voicecommunications over an IP network, as opposed to the PSTN. For example,a user of the mobile computing device 410 may invoke a VoIP applicationand initiate a call using the program. The service provider serversystem 452 may forward voice data from the call to a VoIP service, whichmay route the call over the internet to a corresponding computingdevice, potentially using the PSTN for a final leg of the connection.

An application store 466 may provide a user of the mobile computingdevice 410 the ability to browse a list of remotely stored applicationprograms that the user may download over the network 450 and install onthe mobile computing device 410. The application store 466 may serve asa repository of applications developed by third-party applicationdevelopers. An application program that is installed on the mobilecomputing device 410 may be able to communicate over the network 450with server systems that are designated for the application program. Forexample, a VoIP application program may be downloaded from theApplication Store 466, enabling the user to communicate with the VoIPservice 464.

The mobile computing device 410 may access content on the internet 468through network 450. For example, a user of the mobile computing device410 may invoke a web browser application that requests data from remotecomputing devices that are accessible at designated universal resourcelocations. In various examples, some of the services 460 are accessibleover the internet.

The mobile computing device may communicate with a personal computer470. For example, the personal computer 470 may be the home computer fora user of the mobile computing device 410. Thus, the user may be able tostream media from his personal computer 470. The user may also view thefile structure of his personal computer 470, and transmit selecteddocuments between the computerized devices.

A voice recognition service 472 may receive voice communication datarecorded with the mobile computing device's microphone 422, andtranslate the voice communication into corresponding textual data. Insome examples, the translated text is provided to a search engine as aweb query, and responsive search engine search results are transmittedto the mobile computing device 410.

The mobile computing device 410 may communicate with a social network474. The social network may include numerous members, some of which haveagreed to be related as acquaintances. Application programs on themobile computing device 410 may access the social network 474 toretrieve information based on the acquaintances of the user of themobile computing device. For example, an “address book” applicationprogram may retrieve telephone numbers for the user's acquaintances. Invarious examples, content may be delivered to the mobile computingdevice 410 based on social network distances from the user to othermembers. For example, advertisement and news article content may beselected for the user based on a level of interaction with such contentby members that are “close” to the user (e.g., members that are“friends” or “friends of friends”).

The mobile computing device 410 may access a personal set of contacts476 through network 450. Each contact may identify an individual andinclude information about that individual (e.g., a phone number, anemail address, and a birthday). Because the set of contacts is hostedremotely to the mobile computing device 410, the user may access andmaintain the contacts 476 across several devices as a common set ofcontacts.

The mobile computing device 410 may access cloud-based applicationprograms 478. Cloud-computing provides application programs (e.g., aword processor or an email program) that are hosted remotely from themobile computing device 410, and may be accessed by the device 410 usinga web browser or a dedicated program. Example cloud-based applicationprograms include GOOGLE DOCS word processor and spreadsheet service,GOOGLE GMAIL webmail service, and PICASA picture manager.

Mapping service 480 can provide the mobile computing device 410 withstreet maps, route planning information, and satellite images. Anexample mapping service is GOOGLE MAPS. The mapping service 480 may alsoreceive queries and return location-specific results. For example, themobile computing device 410 may send an estimated location of the mobilecomputing device and a user-entered query for “pizza places” to themapping service 480. The mapping service 480 may return a street mapwith “markers” superimposed on the map that identify geographicallocations of nearby “pizza places.”

Turn-by-turn service 482 may provide the mobile computing device 410with turn-by-turn directions to a user-supplied destination. Forexample, the turn-by-turn service 482 may stream to device 410 astreet-level view of an estimated location of the device, along withdata for providing audio commands and superimposing arrows that direct auser of the device 410 to the destination.

Various forms of streaming media 484 may be requested by the mobilecomputing device 410. For example, computing device 410 may request astream for a pre-recorded video file, a live television program, or alive radio program. Example services that provide streaming mediainclude YOUTUBE and PANDORA.

A micro-blogging service 486 may receive from the mobile computingdevice 410 a user-input post that does not identify recipients of thepost. The micro-blogging service 486 may disseminate the post to othermembers of the micro-blogging service 486 that agreed to subscribe tothe user.

A search engine 488 may receive user-entered textual or verbal queriesfrom the mobile computing device 410, determine a set ofinternet-accessible documents that are responsive to the query, andprovide to the device 410 information to display a list of searchresults for the responsive documents. In examples where a verbal queryis received, the voice recognition service 472 may translate thereceived audio into a textual query that is sent to the search engine.

These and other services may be implemented in a server system 490. Aserver system may be a combination of hardware and software thatprovides a service or a set of services. For example, a set ofphysically separate and networked computerized devices may operatetogether as a logical server system unit to handle the operationsnecessary to offer a service to hundreds of individual computingdevices.

In various implementations, operations that are performed “in response”to another operation (e.g., a determination or an identification) arenot performed if the prior operation is unsuccessful (e.g., if thedetermination was not performed). Features in this document that aredescribed with conditional language may describe implementations thatare optional. In some examples, “transmitting” from a first device to asecond device includes the first device placing data into a network, butmay not include the second device receiving the data. Conversely,“receiving” from a first device may include receiving the data from anetwork, but may not include the first device transmitting the data.

FIG. 5 is a block diagram of computing devices 500, 550 that may be usedto implement the systems and methods described in this document, aseither a client or as a server or plurality of servers. Computing device500 is intended to represent various forms of digital computers, such aslaptops, desktops, workstations, personal digital assistants, servers,blade servers, mainframes, and other appropriate computers. Computingdevice 550 is intended to represent various forms of mobile devices,such as personal digital assistants, cellular telephones, smartphones,and other similar computing devices. Additionally computing device 500or 550 can include Universal Serial Bus (USB) flash drives. The USBflash drives may store operating systems and other applications. The USBflash drives can include input/output components, such as a wirelesstransmitter or USB connector that may be inserted into a USB port ofanother computing device. The components shown here, their connectionsand relationships, and their functions, are meant to be exemplary only,and are not meant to limit implementations described and/or claimed inthis document.

Computing device 500 includes a processor 502, memory 504, a storagedevice 506, a high-speed interface 508 connecting to memory 504 andhigh-speed expansion ports 510, and a low speed interface 512 connectingto low speed bus 514 and storage device 506. Each of the components 502,504, 506, 508, 510, and 512, are interconnected using various busses,and may be mounted on a common motherboard or in other manners asappropriate. The processor 502 can process instructions for executionwithin the computing device 500, including instructions stored in thememory 504 or on the storage device 506 to display graphical informationfor a GUI on an external input/output device, such as display 516coupled to high speed interface 508. In other implementations, multipleprocessors and/or multiple buses may be used, as appropriate, along withmultiple memories and types of memory. Also, multiple computing devices500 may be connected, with each device providing portions of thenecessary operations (e.g., as a server bank, a group of blade servers,or a multi-processor system).

The memory 504 stores information within the computing device 500. Inone implementation, the memory 504 is a volatile memory unit or units.In another implementation, the memory 504 is a non-volatile memory unitor units. The memory 504 may also be another form of computer-readablemedium, such as a magnetic or optical disk.

The storage device 506 is capable of providing mass storage for thecomputing device 500. In one implementation, the storage device 506 maybe or contain a computer-readable medium, such as a floppy disk device,a hard disk device, an optical disk device, or a tape device, a flashmemory or other similar solid state memory device, or an array ofdevices, including devices in a storage area network or otherconfigurations. A computer program product can be tangibly embodied inan information carrier. The computer program product may also containinstructions that, when executed, perform one or more methods, such asthose described above. The information carrier is a computer- ormachine-readable medium, such as the memory 504, the storage device 506,or memory on processor 502.

The high speed controller 508 manages bandwidth-intensive operations forthe computing device 500, while the low speed controller 512 manageslower bandwidth-intensive operations. Such allocation of functions isexemplary only. In one implementation, the high-speed controller 508 iscoupled to memory 504, display 516 (e.g., through a graphics processoror accelerator), and to high-speed expansion ports 510, which may acceptvarious expansion cards (not shown). In the implementation, low-speedcontroller 512 is coupled to storage device 506 and low-speed expansionport 514. The low-speed expansion port, which may include variouscommunication ports (e.g., USB, Bluetooth, Ethernet, wireless Ethernet)may be coupled to one or more input/output devices, such as a keyboard,a pointing device, a scanner, or a networking device such as a switch orrouter, e.g., through a network adapter.

The computing device 500 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as astandard server 520, or multiple times in a group of such servers. Itmay also be implemented as part of a rack server system 524. Inaddition, it may be implemented in a personal computer such as a laptopcomputer 522. Alternatively, components from computing device 500 may becombined with other components in a mobile device (not shown), such asdevice 550. Each of such devices may contain one or more of computingdevice 500, 550, and an entire system may be made up of multiplecomputing devices 500, 550 communicating with each other.

Computing device 550 includes a processor 552, memory 564, aninput/output device such as a display 554, a communication interface566, and a transceiver 568, among other components. The device 550 mayalso be provided with a storage device, such as a microdrive or otherdevice, to provide additional storage. Each of the components 550, 552,564, 554, 566, and 568, are interconnected using various buses, andseveral of the components may be mounted on a common motherboard or inother manners as appropriate.

The processor 552 can execute instructions within the computing device550, including instructions stored in the memory 564. The processor maybe implemented as a chipset of chips that include separate and multipleanalog and digital processors. Additionally, the processor may beimplemented using any of a number of architectures. For example, theprocessor 410 may be a CISC (Complex Instruction Set Computers)processor, a RISC (Reduced Instruction Set Computer) processor, or aMISC (Minimal Instruction Set Computer) processor. The processor mayprovide, for example, for coordination of the other components of thedevice 550, such as control of user interfaces, applications run bydevice 550, and wireless communication by device 550.

Processor 552 may communicate with a user through control interface 558and display interface 556 coupled to a display 554. The display 554 maybe, for example, a TFT (Thin-Film-Transistor Liquid Crystal Display)display or an OLED (Organic Light Emitting Diode) display, or otherappropriate display technology. The display interface 556 may compriseappropriate circuitry for driving the display 554 to present graphicaland other information to a user. The control interface 558 may receivecommands from a user and convert them for submission to the processor552. In addition, an external interface 562 may be provide incommunication with processor 552, so as to enable near areacommunication of device 550 with other devices. External interface 562may provide, for example, for wired communication in someimplementations, or for wireless communication in other implementations,and multiple interfaces may also be used.

The memory 564 stores information within the computing device 550. Thememory 564 can be implemented as one or more of a computer-readablemedium or media, a volatile memory unit or units, or a non-volatilememory unit or units. Expansion memory 574 may also be provided andconnected to device 550 through expansion interface 572, which mayinclude, for example, a SIMM (Single In Line Memory Module) cardinterface. Such expansion memory 574 may provide extra storage space fordevice 550, or may also store applications or other information fordevice 550. Specifically, expansion memory 574 may include instructionsto carry out or supplement the processes described above, and mayinclude secure information also. Thus, for example, expansion memory 574may be provide as a security module for device 550, and may beprogrammed with instructions that permit secure use of device 550. Inaddition, secure applications may be provided via the SIMM cards, alongwith additional information, such as placing identifying information onthe SIMM card in a non-hackable manner.

The memory may include, for example, flash memory and/or NVRAM memory,as discussed below. In one implementation, a computer program product istangibly embodied in an information carrier. The computer programproduct contains instructions that, when executed, perform one or moremethods, such as those described above. The information carrier is acomputer- or machine-readable medium, such as the memory 564, expansionmemory 574, or memory on processor 552 that may be received, forexample, over transceiver 568 or external interface 562.

Device 550 may communicate wirelessly through communication interface566, which may include digital signal processing circuitry wherenecessary. Communication interface 566 may provide for communicationsunder various modes or protocols, such as GSM voice calls, SMS, EMS, orMMS messaging, CDMA, TDMA, PDC, WCDMA, CDMA2000, or GPRS, among others.Such communication may occur, for example, through radio-frequencytransceiver 568. In addition, short-range communication may occur, suchas using a Bluetooth, WiFi, or other such transceiver (not shown). Inaddition, GPS (Global Positioning System) receiver module 570 mayprovide additional navigation- and location-related wireless data todevice 550, which may be used as appropriate by applications running ondevice 550.

Device 550 may also communicate audibly using audio codec 560, which mayreceive spoken information from a user and convert it to usable digitalinformation. Audio codec 560 may likewise generate audible sound for auser, such as through a speaker, e.g., in a handset of device 550. Suchsound may include sound from voice telephone calls, may include recordedsound (e.g., voice messages, music files, etc.) and may also includesound generated by applications operating on device 550.

The computing device 550 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as acellular telephone 580. It may also be implemented as part of asmartphone 582, personal digital assistant, or other similar mobiledevice.

Various implementations of the systems and techniques described here canbe realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof.These various implementations can include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device, and at least one output device.

These computer programs (also known as programs, software, softwareapplications or code) include machine instructions for a programmableprocessor, and can be implemented in a high-level procedural and/orobject-oriented programming language, and/or in assembly/machinelanguage. As used herein, the terms “machine-readable medium”“computer-readable medium” refers to any computer program product,apparatus and/or device (e.g., magnetic discs, optical disks, memory,Programmable Logic Devices (PLDs)) used to provide machine instructionsand/or data to a programmable processor, including a machine-readablemedium that receives machine instructions as a machine-readable signal.The term “machine-readable signal” refers to any signal used to providemachine instructions and/or data to a programmable processor.

To provide for interaction with a user, the systems and techniquesdescribed here can be implemented on a computer having a display device(e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor)for displaying information to the user and a keyboard and a pointingdevice (e.g., a mouse or a trackball) by which the user can provideinput to the computer. Other kinds of devices can be used to provide forinteraction with a user as well; for example, feedback provided to theuser can be any form of sensory feedback (e.g., visual feedback,auditory feedback, or tactile feedback); and input from the user can bereceived in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in acomputing system that includes a back end component (e.g., as a dataserver), or that includes a middleware component (e.g., an applicationserver), or that includes a front end component (e.g., a client computerhaving a graphical user interface or a Web browser through which a usercan interact with an implementation of the systems and techniquesdescribed here), or any combination of such back end, middleware, orfront end components. The components of the system can be interconnectedby any form or medium of digital data communication (e.g., acommunication network). Examples of communication networks include alocal area network (“LAN”), a wide area network (“WAN”), peer-to-peernetworks (having ad-hoc or static members), grid computinginfrastructures, and the Internet.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

Although a few implementations have been described in detail above,other modifications are possible. Moreover, other mechanisms fordisambiguating ambiguous user input be used. In addition, the logicflows depicted in the figures do not require the particular order shown,or sequential order, to achieve desirable results. Other steps may beprovided, or steps may be eliminated, from the described flows, andother components may be added to, or removed from, the describedsystems. Accordingly, other implementations are within the scope of thefollowing claims.

1-7. (canceled)
 8. A non-transitory computer-readable medium encodedwith a computer program comprising instructions that, when executed,operate to cause a computer to perform operations comprising: receiving,by the computer, an input that is able to be represented by either oftwo or more homophones, homonyms, or heteronyms; determining, by thecomputer, a current context associated with a mobile device; applying,by the computer, the current context to one or more rules to select oneof the two or more homophones, homonyms, or heteronyms as representingthe input; and outputting, by the computer responsive to applyingselecting the context to the one or more rules, the selected homophone,homonym, or heteronym as representing the input.
 9. The medium of claim8, wherein: the current context comprises a direction of travelassociated with the mobile device, and applying the current context tothe one or more rules comprises determining that the direction of travelpoints to a location associated with the selected homophone, homonym, orheteronym.
 10. The medium of claim 8, wherein: the current contextcomprises a distance to one or more contacts stored in a contactdatabase on the mobile device, and applying the current context to theone or more rules comprises determining that the distance to the one ormore contacts is within a predefined range.
 11. The medium of claim 8,wherein: the current context comprises a level of background noise, andapplying the current context to the one or more rules comprisesdetermining that the level of background noise is greater than apredefined value.
 12. The medium of claim 8, wherein: the currentcontext comprises a rate of speed of the mobile device, and applying thecurrent context to the one or more rules comprises determining that therate of speed of the mobile device exceeds a predefined value.
 13. Themedium of claim 8, wherein: the context comprises an availability of oneor more wireless networks, and applying the current context to the oneor more rules comprises determining that the one or more wirelessnetworks are available.
 14. The medium of claim 8, wherein: the contextcomprises an existence of a connection between the mobile device and aparticular wireless network, and applying the current context to the oneor more rules comprises determining that the existence of the connectionbetween the mobile device and the particular wireless network exists.15. The medium of claim 8, wherein: the context comprises an existenceof a connection between the mobile device and another, different device,and applying the current context to the one or more rules comprisesdetermining that the connection between the mobile device and the other,different device exists.
 16. The medium of claim 8, wherein: the contextcomprises an identity of one or more contacts that have recently beencalled using the mobile device, and applying the current context to theone or more rules comprises determining that the identity of the one ormore contacts matches the selected homophone, homonym, or heteronym. 17.The medium of claim 8, wherein: the context comprises a dock status ofthe mobile device, and applying the current context to the one or morerules comprises determining that the mobile device is docked for use ina vehicle, and in response selecting the selected homophone, homonym, orheteronym based on the selected homophone, homonym, or heteronym beingassociated with a navigation command.
 18. The medium of claim 8,wherein: the context comprises one or more appointments on a calendarstored on the mobile device, and applying the current context to the oneor more rules determining that information associated with the one ormore appointments on the calendar matches the selected homophone,homonym, or heteronym.
 19. The medium of claim 8, wherein determining acurrent context associated with a mobile device comprises: determining acurrent context associated with one or more other devices, andidentifying the current context associated with the mobile device basedat least in part on the current context associated with the one or moreother devices. 20-23. (canceled)
 24. A computer-implemented method,comprising: receiving, by a computer, an input that is able to berepresented by either of two or more homophones, homonyms, orheteronyms; determining, by the computer, a current context associatedwith a mobile device; applying, by the computer, the current context toone or more rules to select one of the two or more homophones, homonyms,or heteronyms as representing the input; and outputting, by the computerresponsive to applying selecting the current context to the one or morerules, the selected homophone, homonym, or heteronym as representing theinput.
 25. The method of claim 24, wherein: the current contextcomprises a direction of travel associated with the mobile device, andapplying the current context to the one or more rules comprisesdetermining that the direction of travel points to a location associatedwith the selected homophone, homonym, or heteronym.
 26. The method ofclaim 24, wherein: the current context comprises a distance to one ormore contacts stored in a contact database on the mobile device, andapplying the current context to the one or more rules comprisesdetermining that the distance to the one or more contacts is within apredefined range.
 27. The method of claim 24, wherein: the currentcontext comprises a level of background noise, and applying the currentcontext to the one or more rules comprises determining that the level ofbackground noise is greater than a predefined value.
 28. The method ofclaim 24, wherein: the current context comprises a rate of speed of themobile device, and applying the current context to the one or more rulescomprises determining that the rate of speed of the mobile deviceexceeds a predefined value.
 29. The method of claim 24, wherein: thecontext comprises an availability of one or more wireless networks, andapplying the current context to the one or more rules comprisesdetermining that the one or more wireless networks are available. 30.The method of claim 24, wherein: the context comprises an existence of aconnection between the mobile device and a particular wireless network,and applying the current context to the one or more rules comprisesdetermining that the existence of the connection between the mobiledevice and the particular wireless network exists.
 31. The method ofclaim 24, wherein: the context comprises an existence of a connectionbetween the mobile device and another, different device, and applyingthe current context to the one or more rules comprises determining thatthe connection between the mobile device and the other, different deviceexists.
 32. The method of claim 24, wherein: the context comprises anidentity of one or more contacts that have recently been called usingthe mobile device, and applying the current context to the one or morerules comprises determining that the identity of the one or morecontacts matches the selected homophone, homonym, or heteronym.
 33. Themethod of claim 24, wherein: the context comprises a dock status of themobile device, and applying the current context to the one or more rulescomprises determining that the mobile device is docked for use in avehicle, and in response selecting the selected homophone, homonym, orheteronym based on the selected homophone, homonym, or heteronym beingassociated with a navigation command.
 34. The method of claim 24,wherein: the context comprises one or more appointments on a calendarstored on the mobile device, and applying the current context to the oneor more rules determining that information associated with the one ormore appointments on the calendar matches the selected homophone,homonym, or heteronym.
 35. The method of claim 24, wherein determining acurrent context associated with a mobile device comprises: determining acurrent context associated with one or more other devices, andidentifying the current context associated with the mobile device basedat least in part on the current context associated with the one or moreother devices.